KILLER WOLF'S PROFILE

I find this a lot more relaxing, but there was no science involved.

I haven't had an occasion to try the ignore feature out yet, and sort of seriously doubt I'll ever get one.

I think, maybe, as a best case scenario, it could be a positive thing. People might be less inclined to "act the fool" if they know they can be completely written off for it. A little more posting responsibility makes for a cleaner forum for all.

As a worst case scenario, I can see it being abused as the ultimate ostrich method for "winning" an argument. You disagree, you criticize, you prompt thought provoking discussions? IGNORE.

Also, is there any notification to the ignored, or do they just blissfully continue to shout into a vacuum?

I always try to couch subjects I'm not that knowledgeable about in things that I know very well. I have found, several times, that too much research tends to make things very dry.

There is almost a compulsion to try and wedge as much "cool facts" and "interesting data" into the end work as possible, which can really detract from the story and overall feel of a piece.

My achievements for the Secret Santa review event came in overnight, so I guess I'll be a little higher up the list next month, unless everyone else slingshots past me =)

What I'm doing for one of my projects goes something like this:

First, I record the boss's stats into a few variables. If you're using a scan power, you probably already have one of these laying around. I bounce out of the battle every turn to reference a master common event. In the event I check for things like hero is in Status X, hero has Item X equipped, Hero's Stat is >= X.

Then, I use that info to toggle a group of switches. These switches also happen to be triggers for the Boss's skills/behaviors. Some of these might have to be specially evented (if you want a specific attack to strike a specific party member reliably). That way the boss can respond to the player, strip them of their buffs after a couple of rounds, paralyze the one holding the +5 Weapon of Boss Kill, and even apply status ailments to party members whose stats are too high for comfort.

Since you're recording boss stats into variables, you can also check to see what status ailments they are suffering from (if they effect stats). This way you can have the boss counter the debuffs every now and then, forcing the team to have to adapt on the fly instead of just "spam status effects, spam heavy hits, heal every turn, victory!"

You can also have multiple copies of the same boss, but with different resistances and statistics. You can switch it based on hp/mp levels, or through switches that you control with your master common event.

Just hammering on the same attack every turn is no fun. If you have the boss's weaknesses and strengths changing dynamically (when applicable via story/boss type/whatever), it should make for a more fun and engaging battle!